home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Suzy B Software 2
/
Suzy B Software CD-ROM 2 (1994).iso
/
bootup
/
boot_a2m
/
movpic20
/
movpic20.asc
< prev
next >
Wrap
Text File
|
1995-05-02
|
9KB
|
201 lines
o o o o o o o o o o o o o o o
o o
o Moving Pictures v2.0 o
o Saturday, February 20, 1993 o
o By Terry May @ Shark Bytes o
o o
o o o o o o o o o o o o o o o
VERSIONS:
1.0 30-Mar-92 ... Original release!
1.1 01-Jul-92 ... Support for Degas Elite (.PC?) background pics
dropped in favor of the smaller Tiny (.TN?) format.
1.2 28-Jan-93 ... Added support for Extend-O-Save (.EXT) files.
2.0 20-Feb-93 ... No longer tied to specific file types. Now
the user supplies file types with MOVEPICS.LST!
The possibilities are endless! :^)
INTRODUCTION:
Moving Pictures came about while I was beta testing Warp 9 v3.5 from
CodeHead Technologies. Background pics on my ST was a new
experience, and I found it really added a lot to my computing
environment. My only complaint was that I had the same background
pic each time I booted up, unless I manually renamed another pic. I
decided random background pics would be much more enjoyable, and
thus, Moving Pictures was born.
Moving Pictures was initially designed to randomize Warp 9
background pics and Desk Manager startup pics, and was tied
specifically to these file types. Then along came Warp 9
Extend-O-Save, and I thought it would be neat to have random screen
savers. Well, then came Mandala, and I decided it would be neat to
have random palettes for IT!
Obviously, I like a little variety in my life, but it was becoming a
bit ridiculous to keep updating Moving Pictures for every time a new
file type came out that I wanted to randomize. I decided it was
time to make Moving Pictures more flexible, to easily handle not
only all current file types I want to randomize, but any future
ones, as well. And so, I updated Moving Pictures to v2.0 for
exactly this purpose. It will now randomize not only all your
pictures, but anything else you like!
INSTALLATION:
First, copy MOVEPICS.PRG to your AUTO folder. It can be placed
anywhere in your AUTO folder, since it's not a TSR and doesn't do
anything with your memory or vectors. I like to run it last, just
because it takes a couple seconds, allowing me to review the
messages from the programs that run before it. :^)
Second, create an ASCII file called MOVEPICS.CTL (a sample is
included) and also place it in your AUTO folder. Again, order is
unimportant. Each line in this file MUST follow a strict format, as
follows:
Source path\filespec starting in the first column, followed by
EXACTLY ONE SPACE, followed by the destination path\filename. The
source path\filespec MUST contain some type of wildcard, e.g.,
C:\Pics\*.TN1. The destination path\filename MUST contain the EXACT
filename you want for your destination file. Both source and
destination MUST contain full paths. Case is unimportant.
The source should be the folder containing all the files you wish to
randomize. The destination should be the exact filename needed by
the program that uses that file.
IMPORTANT: Both source and destination MUST be on the same drive.
There is no check for this, so you WILL get an error if your source
and destination are on different drives. The reason for this is
because Moving Pictures actually renames your files for optimum
speed, and this is not possible between different drives. They
DON'T have to be in the same folder, however.
Here are some examples of _good_ MOVEPICS.CTL entries:
C:\Auto\DeskMgr\*.SPC C:\Auto\DeskMgr\DeskMgr.SPC
C:\Auto\Pictures\*.TN2 C:\Auto\Pictures\STmedium.TN2
C:\Pictures\*.TN3 C:\Warp_9\SThigh.TN3
C:\Prism\*.PN5 C:\Auto\Warp_9\TTmedium.PNT
Here are some examples of _bad_ MOVEPICS.CTL entries:
C:\Auto\DeskMgr\*.SPC C:\Auto\DeskMgr\DeskMgr.SPC
C:\Auto\Pictures\*.TN2 C:\Auto\Pictures\STmedium.TN2
C:\Auto\Pictures\SThigh.TN3 C:\Auto\Pictures\*.TN3
D:\Pictures\*.PC3 C:\Warp_9\SThigh.PC3
The first line has an extra space between source and destination.
The second line has a space at the beginning of the line.
The third line has source and destination backwards.
The fourth line has different source and destination drives.
MOVEPICS.LST:
Moving Pictures creates an ASCII file called MOVEPICS.LST in your
AUTO folder. This file contains a list of the files it has renamed.
The list is in the following format:
C:\AUTO\WARP_9\STMEDIUM.TN2 C:\PICTURES\SHARK.TN2
The first path\filename is the file as it is named now. The second
path\filename is the original path\filename.
Each time Moving Pictures runs, it looks for MOVEPICS.LST in your
AUTO folder and uses it to rename all your files back to their
original path\filenames. It then proceeds to randomize your files
using your MOVEPICS.CTL file and then creates a new MOVEPICS.LST.
If you change your MOVEPICS.CTL file, that's perfectly fine. It will
have no effect whatsoever on Moving Pictures ability to process your
MOVEPICS.LST.
TROUBLESHOOTING:
About the only way to screw up Moving Pictures is to move or rename
the files in that MOVEPICS.LST, or to have your MOVEPICS.LST lost or
corrupted somehow.
If you encounter an error, check your MOVEPICS.LST and make sure it
is not corrupted. If everything looks ok, check each line and
ensure that the SECOND path\filename does not already exist. If it
does, you'll have to delete that line from your MOVEPICS.LST, as
there is no way for Moving Pictures to rename a file to a
destination file that already exists!
If you somehow lost your MOVEPICS.LST, you'll have to go through
each SECOND path\filename in your MOVEPICS.CTL file, and make sure
the path\filename does not already exist, for the same exact reason
outlined above. If so, you'll have to rename the file back to its
original filename.
I may eventually put in some error trapping to check for existance
of the destination path\filenames, but I don't want to bog the
program down anymore than I have to. The program needs to be as
fast as possible, and so the user must assume a little
responsibility for proper operation.
If you get the same destination files two or more times in a row,
don't worry. Your previous destination file goes back into the pool
to be randomized and could very well come up again. The more files
you have in your source folder, the less likely this will happen,
and the greater the random effect.
POSSIBLE USES:
Just about anything! Warp 9 background pics (of ANY flavor now!);
Warp 9 Extend-O-Save modules; palettes for the Mandala EOS module;
IMG files for the Soft-Sci module; Desk Manager startup pics; samples
for Dave Baggett's BEEP.PRG; etc.
Anything that can use a variety of a file type can be enhanced by
Moving Pictures ability to randomize that file type. The only limit
is your imagination (and all the other limits mentioned above. ;^)
WARRANTY:
There is none. Neither myself, Terry May, nor Shark Bytes assume
any responsibility for the use or misuse of Moving Pictures. Moving
Pictures is believed to be perfectly safe in every way, but you still
must USE IT AT YOUR OWN RISK.
If you encounter any bugs, let me know and I'll do my best to fix
them, but I make no promises. (Hey, it's FREE! ;^) If you have any
comments or suggestions, those will be appreciated.
My address is OUTRIDER on both GEnie and Delphi. I can also be
contacted at The Rebel BBS @ 702/435-0786 (Outrider), or through
FidoNet @ 1:209/745.0, AtariNet @ 51:2/0.0 and NeST @ 90:300/1012.
POSTCARDWARE:
What? PostCardWare? Yep, if you use Moving Pictures, you are asked to
send a postcard of your home town to the following address:
Atari Envy Inc.
10871 1/2 Whipple Street
N. Hollywood, CA 91602
Your postcard WILL be appreciated!
COPYRIGHTS:
"Moving Pictures" is a copyright of Shark Bytes. It may be
distributed freely, provided it is accompanied by this documentation
in complete and unaltered form.